-
Notifications
You must be signed in to change notification settings - Fork 140
Fix UTF-16LE line endings in dni/ini files #708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Fix UTF-16LE line endings in dni/ini files #708
Conversation
mike-clark-8192
commented
Jan 9, 2026
- Three files had corrupted single-byte CRLF (0d 0a) mixed with UTF-16LE content, breaking git's working-tree-encoding conversion
- Corrected to proper UTF-16LE CRLF (0d 00 0a 00) so files round-trip correctly through git
|
I cannot find the single word 0D0A in AltSnap.dni file nor in fr_FR.ini, However ko_KR.ini seems to be utf-8 encoded. It seems you are actually converting to UTF-8 some files? I do not understant what github is doing with encoding, maybe I should remove the .gitattributes flags, and treat those files like binary blobs. |
|
I think I ran into issues with EOL conversions interacting badly with the character encoding confusion, so the content of my pull request is probably not very helpful. However, I did some more research, which led me to this recipe. I tested it and it appears to work. It may seem overly complex, but I wasn't able to simplify it further. I hope this helps. |
edd72e5 to
4fbf88f
Compare
|
@RamonUnch I applied my fix to my feature branch (and thus to this PR). After making these clones, use a directory diff tool diffing ./AS-RU/ and ./AS-MC/ |